RYO Desktop Supplemental Docs:

PRV?


What is a PRV?  A neat little acronym for "Public Reception Version".  What does that mean?  Well...

Basically this version is being released while still in the development/concept stage in order to see what folks think of it.  I'm quite fond of the application for my own purposes, so I will continue to play with it on my own until I lose interest.  The app will go on, for me at least.  

However, creating a release for your own personal use and a distributable version suitable for presentation to the world at large is another step altogether.  A public release requires a lot of niceties I don't need myself.  It requires a great deal more error checking.  And it also requires a certain adherence to the data file standard so that everyone's creations don't get trashed when they upgrade to the latest version.

This app has a long way to go.  In particular, the workaround concerning the sizing of objects in design mode is horrible.  There are a ton of new objects I hope to implement beyond the "starter set" you see here.  Lots and lots of improvements to be made.  I have a nice chunk of text file full of ideas I've had on the side during development and suggestions that "pre-PRV" users have made.  And I want to make sure I'm concentrating on the worthwhile elements in the few hours I set aside to code.

So, this version is released to kind of gather public opinion - on the application to a smaller degree and the concept to a larger one.  This app will continue to spawn on my own hard drive - whether the net sees another version hit the pipes depends greatly on the amount of positive user response I get.  If I'm going to continue coding this thing, I want to spend the time where it's most useful.  If the general public wants to see it happen, then my time is well spent preparing a networthy version.  If response is cool or noncommittal, then I'll spend my time coding for myself without taking into account things that might make others' lives miserable (file format changes, nonexistant error codes, support of obscure third party controls, updates for NT/98/etc.)

I'd like to hear from you about this app/implementation/concept.  Positive or negative.  Email is cheap and you don't have to write a volume if you don't care to.  I want to know what about the app annoyed you, what you liked, what messed up.  I want to know if you like the idea of the application even if the app itself didn't quite live up to your fancies.  I want to know if this app replaced another you were using, or _almost_ replaced it and why it did/didn't.  

And since I'm asking you to divulge, I'll tell you where I see the app going. Turnabout is fair play, after all:

I'd like to see this application become powerful enough to totally replace the Windows shell someday.  No more Start Menu, desktop icons, right click menus, etc.  I'd also like to see it flexible enough to serve you well as a simple addition to the current Windows shell without carrying a vast amount of bloat.  I'd like it to be able to replace Windows functionality to whatever degree you choose without getting in the way of the functions of Windows you choose to continue utilizing.  I'm afraid that although Microsoft has the ability to implement this kind of solution, the users will constantly be bowing to whatever standard they intend to force upon us.  Hey, I was really hoping to be able to do all this stuff with Active Desktop, but security concerns (I suppose) won't even let you launch a single program cleanly from the browser.  So in that light, I'd like to give people another option, if they're interested.

I'd immediately like to improve the user interface - especially in the design mode.  I don't intend to leave it as shabby as it is forever :)  I'd also like to make the object options a good deal more flexible - allowing for actions and multiple actions or internal scripts to be fired by any number of actions (keystrokes, mouse moves, single/double/left/right/ both clicks, system/folder/file level events, etc.)  I also have plans for a wide variety of objects that will introduce additional functionality like the time/date object - disk space indicators, "folder watchers", active menus, folder views, etc.  I'd also like to plug the app into the net for information gathering and presentation purposes that cater to the home dial-up user as well as the constantly connected network client (I feel like things similar to Active Desktop elements heavily rely on you to have a constant connection to be valuable).

I plan to spend whatever coding time I can on this app.  If the users cry out in joy across the world, I'll probably try to work on this to the exclusion of other offerings I occasionally distribute.  Otherwise, it'll just become my little fun project to play with on rainy weekends and you'll probably see version 1 quietly slip from the bandwidth.

I plan to keep this application freeware.  I won't guarantee it - it's possible that it could become a little too popular for my own ability to support it and require that I ask for a fee.  But I'm quite enchanted with the idea of freeware, so you shouldn't expect me to start charging for it as soon as I think it's in demand.  To be honest, your average "shareware registration" fee might buy me a lunch; maybe two if I charge beyond its value.  A heartfelt appreciative email gives me the kind of good feeling that will carry me for months at a time.

So that's what a PRV is and what I hope you'll do about it.  That's the story I'm going with.